Immediate Rendering callback #592
Conversation
…echanism requires modification of the WebGLRenderer for different objects. The new implementation leaves the current MarchingCubes immediate renderer intact but checks for existence of a immediateRenderCallback member function of the object. If found, that object is added to the scene.__webglObjectsImmediate array. The program, webgl context, and frustum are currently passed into the callback, putting al rendering responsibility at the implementing object. This may break the Three.js abstraction somewhat, but allows "power users" to do some funky webgl stuff while still relying on the Three.js framework for the rest of the scene...
|
@alteredq: is it good to merge then? this goes a bit over my head right now :) |
|
I guess so, this is still very early stage of such feature, we'll put it in and see where it'll go (usual procedure - collect enough use cases and keep refactoring). |
|
Merged. Thanks @NINE78! :) |
|
My pleasure; I hope others get some use out of this! I mainly use it to recursively traverse a LOD quadtree, and for another object to do some funky stencil buffer stuff... As said before, I'm not quite sure this is the "cleanest" way of doing it, but since JS doesn't have any proper prototype/interface mechanism, it's the best I could come up with. But I do feel confident there is room in there for a "custom renderer pipeline" much like to ability to have custom shaders... |
Added "lower level" immediate rendering functionality. The existing mechanism requires modification of the WebGLRenderer for different objects. The new implementation leaves the current MarchingCubes immediate renderer intact but checks for existence of a immediateRenderCallback member function of the object. If found, that object is added to the scene.__webglObjectsImmediate array. The program, webgl context, and frustum are currently passed into the callback, putting al rendering responsibility at the implementing object. This may break the Three.js abstraction somewhat, but allows "power users" to do some funky webgl stuff while still relying on the Three.js framework for the rest of the scene...